Repository navigation
ci: build a console image and deploy it to the K3s cluster - #1
Merged
Merged
Conversation
Higress moved from the Docker host 207.57.124.102 to the K3s cluster (namespace higress). The workflow no longer uploads the jar over SSH and builds the image on the server: - image job: builds deploy/Dockerfile (console jar on top of the Higress all-in-one, now pinned by digest instead of a server-local tag) and pushes docker.io/<DOCKER_USERNAME>/higress-console:<version> - deploy job: pre-pulls the image on the node with a throw-away pod so the Recreate rollout never stops the running gateway for an unpullable image, applies deploy/k3s/higress.yaml, waits for readiness, rolls back on failure and checks that mcp.tmlab.top still enforces auth - add deploy/k3s/higress.yaml (the manifest running in the cluster) and update deploy/README.md - needs repository secret KUBE_CONFIG (ServiceAccount higress/ci-deployer); DEPLOY_HOST/USER/SSH_KEY/KNOWN_HOSTS are no longer used Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Production moved from Docker on 207.57.124.102 to the K3s cluster (
k3s.seasonschange.cn) on 2026-11-11. The service is already running there; this PR only changes how releases reach it.Changes
imagejob: buildsdeploy/Dockerfileand pushesdocker.io/<DOCKER_USERNAME>/higress-console:<version>. The Dockerfile puts the console jar on top of the Higress all-in-one image, which is now pinned by digest instead of the server-localhigress-aio-base:pinnedtag (same digest55f5fa3e…)deployjob:Recreate, so this makes sure the running gateway is never stopped for an image the node cannot pulldeploy/k3s/higress.yamland waits for console readiness, runningrollout undoon failuremcp.tmlab.topstill rejects unauthenticated MCP calls with 401deploy/k3s/higress.yaml, the manifest running in the cluster, and updatesdeploy/README.mdVerification
kubectl diffwith the CI account: the only difference from the running Deployment isimagePullPolicy(Never → IfNotPresent)tmllab/higress-consoleSecrets
KUBE_CONFIGis set: a kubeconfig for ServiceAccounthigress/ci-deployerDEPLOY_HOST,DEPLOY_USER,DEPLOY_SSH_KEYandDEPLOY_KNOWN_HOSTSare no longer usedNote: merging triggers a deploy, because the workflow and
deploy/**changed.🤖 Generated with Claude Code